Skip to content

chore: update dependency nunit.analyzers to 4.12.0#714

Open
renovate-bot wants to merge 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/nunit.analyzers-4.x
Open

chore: update dependency nunit.analyzers to 4.12.0#714
renovate-bot wants to merge 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/nunit.analyzers-4.x

Conversation

@renovate-bot
Copy link
Contributor

This PR contains the following updates:

Package Change Age Confidence
NUnit.Analyzers 4.11.24.12.0 age confidence

Release Notes

nunit/nunit.analyzers (NUnit.Analyzers)

v4.12.0: NUnit Analyzers 4.12 - March 3, 2026

Compare Source

NUnit Analyzers 4.12 - March 3, 2026

This release of the NUnit Analyzers improves NUnit1029 to account for TestCaseSource
support for params and optional arguments. It also introduces a new analyzer for incorrect
usage of Is.Not.Null.Or.Empty, fixes regressions in NUnit2005 and NUnit2055, and updates
NUnit package dependencies.

The release contains contributions from the following users (in alphabetical order):

Issues Resolved

Features and Enhancements

  • #​957 Relax NUnit1029 for TestCaseSource where method accepts a single "params" array
  • #​189 Warning when Is.Not.Null.Or.Empty used

Bugs

  • #​953 Code fix for NUnit2055 can generate invalid code for classic asserts
  • #​952 Code fix for NUnit2005 tries to use Is.Empty constraint on incompatible types.

Tooling, Process, and Documentation

  • #​973 chore: Bump NUnit version
  • #​970 chore: Bump NUnit to version 4.5.0
  • #​967 Fix note about works with Unity Test Framework
  • #​937 chore: bump version

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested review from a team as code owners March 7, 2026 16:58
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 7, 2026
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the NUnit.Analyzers dependency to its latest version, 4.12.0. This upgrade incorporates several enhancements and bug fixes, including refined support for TestCaseSource in NUnit1029, the addition of a new analyzer for Is.Not.Null.Or.Empty usage, and corrections to existing analyzer code fixes. These changes aim to improve the accuracy and robustness of NUnit test analysis within the project.

Highlights

  • Dependency Update: Updated the NUnit.Analyzers dependency from version 4.11.2 to 4.12.0.
  • Analyzer Improvements: Improved NUnit1029 to support TestCaseSource with params and optional arguments.
  • New Analyzer: Introduced a new analyzer to detect incorrect usage of Is.Not.Null.Or.Empty.
  • Bug Fixes: Fixed regressions in the code fixes for NUnit2005 and NUnit2055.
Changelog
  • spanner-ado-net/spanner-ado-net-samples-tests/spanner-ado-net-samples-tests.csproj
    • Updated NUnit.Analyzers package version to 4.12.0.
  • spanner-ado-net/spanner-ado-net-tests/spanner-ado-net-tests.csproj
    • Updated NUnit.Analyzers package version to 4.12.0.
Activity
  • This pull request was automatically generated by Renovate Bot to update the NUnit.Analyzers dependency.
  • Automatic merging is currently disabled, requiring manual review and merge.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the NUnit.Analyzers dependency from version 4.11.2 to 4.12.0. This is a routine dependency update that brings bug fixes and improvements to the static analysis tools. The changes in the project files are correct, and I see no issues with this update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kokoro:force-run Add this label to force Kokoro to re-run the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant